Additional Memory for Live Data Caches

If you use the live data caches in N4, you need additional RAM on each N4 node (including the center and standby nodes), depending upon the terminal's operations load. Since the live data caches are built during node startup and reside in the memory of each node in a cluster, it is a resource-intensive feature. Therefore, the setting for live data caches is turned off by default.

You must turn on the live data caches if your terminal is fully automated and using these features in N4:

VMT / Control Room UI

POW Monitor view (Operations Control POW Monitor)
ASC Schedule Monitor view (Operations Control ASC Schedule Monitor)
Automation customers using the Block Impact Minimizer and the Intra-block Decker with live data cache

IMPORTANT: All customers should notify their Navis Professional Services contact before turning on LDC.

Use the following formula to estimate how much additional memory you may need for each N4 node when using live data caches:

Additional memory = [Number of active units x 20 KB] + [1 GB]

Table 4: Sample Calculations for Additional Memory

Machine Memory Requirement		Peak Active Units in Terminal¹
Machine Memory Requirement		50,000 units	200,000 units
Memory required for active units	x 20 KB/unit	1.0 GB ²	4 GB
Memory to account for processing updates for live data caches	+	1 GB	1 GB
Total additional memory required for live data caches	=	2 GB	5 GB
Required RAM without live data caches	+	12 GB	12 GB
Total RAM on N4 node with live data caches	=	14 GB	17 GB

¹ Number of active units. This is generally the number of containers visible in the XPS client. This includes units where the unit visit state is Active, but also departed, pre-advised, and in the yard.

² If the total RAM is a fraction, you can round up to account for future growth.

Table 5: Database Hosts

Component	Typical Host Quantity	CPU ⁽¹⁾	RAM	Disk Space	Windows Server 2022	Windows Server 2019	Windows Server 2016	Red Hat Enterprise Linux 8.x	Red Hat Enterprise Linux 7.x
N4 Database Host (For more details, see p. 1)	1 minimum	See Database Host Size Based on Annual TEU (on page 1).							
N4 Billing Database Host (For more details, see p. 1)	1	4 cores	16 GB	550 GB					
ECS Database Host	1	Refer to ECS vendor for OS and software requirements.

¹Physical or virtual cores, 2.5 GHz or faster

The database host requirements vary with Annual TEU. For recommended guidelines, see Database Host Size Based on Annual TEU (on page 1).

Navis acknowledges that Oracle and Microsoft support many operating systems other than those listed within the Navis N4: Application Environment Guide. Customers are welcome to utilize an operating system of their choosing with Oracle or SQL Server, subject to Oracle or Microsoft support, but due to limited knowledge surrounding all variations do so at their own risk. They will be fully responsible for the maintenance and support of this system. Therefore, Navis strongly recommends that the customer staffs a skilled database administrator who can adequately support the system.

Table 6: Client Workstations

Component	CPU ⁽¹⁾	RAM	Disk Space	Windows 10	Windows 11
N4 Client Workstation	2 cores	2 GB	100 GB		
XPS Client	2 cores	4 GB ⁽²⁾	60 GB		
Equipment Control System Client	Refer to ECS vendor for OS and software requirements.

¹Physical or virtual cores, 2.5 GHz or faster

² If you are running more than one XPS client application (such as XD or PrimeRoute) on the same workstation:

For sites under 3 million annual TEU, add 1 GB for each additional XPS client application.
For sites over 3 million annual TEU, add 2 GB for each additional XPS client application.